Repository navigation
Conversation
cache.ruby-lang.org publishes mswin builds of the 3.4 and 4.0 releases, so `mswin-X.Y` installs them and `mswin-head` the master build. `mswin` and `ruby-mswin` keep installing master until their known users move to `mswin-head`. 3.3 and older are left out because their mkmf ignores ENV['PKG_CONFIG'] and would not use the vcpkg pkgconf. mswin is CRuby built with MSVC, so it stays the ruby engine and the CRuby rules apply. `common.inputs.mswin` only selects the builds and keeps them out of the tool cache, where runners hold RubyInstaller builds of the same versions, and in their own bundler-cache key. Co-authored-by: なつき <i@ntk.me> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The README said what mswin is but not when to use it, which leaves users unsure which of the two Windows builds to choose. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hsbt
force-pushed
the
claude/unruffled-montalcini-d4ed93
branch
from
November 18, 2026 10:26
14493a1 to
c82cc17
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds the release builds split out of #971. cache.ruby-lang.org publishes mswin builds of the 3.4 and 4.0 releases, so
mswin-3.4installs the latest 3.4.x andmswin-headthe master build.Nothing changes for existing users, as
mswinandruby-mswinstill install the master build. larskanis suggested in #972 (comment) thatmswinshould install the latest release. I'll do that in a follow-up, after sending PRs that move the public workflows testing master withmswintomswin-head. I'll take care of the ruby org repositories like ruby/openssl.The README now says when to pick
mswinover the default RubyInstaller builds. I build and publish the mswin packages in ruby/actions and will maintain their support here.mswin is CRuby built with MSVC, not another implementation, so it stays the
rubyengine and goes through every CRuby rule. A flag only selects the mswin builds and keeps them apart from the RubyInstaller builds of the same versions in the tool cache and the bundler-cache key.I ran the built
dist/index.json my x64 and arm64 Windows machines.mswin,ruby-mswinandmswin-headinstalled the master build,mswin-3.4installed 3.4.12, and the mswin steps oftest.ymlpassed.Generated with Claude Code